Project Coordinates and Model Delivery

All discipline models shall use a common coordinate and level system to ensure consistent model alignment throughout the project. This approach supports reliable coordination between disciplines, accurate information exchange, and a controlled handover of verified information.

Model Delivery

Confirm what information will be shared, who delivers it, how often, and in what format.

Information Team Frequency Format
Architectural Model Architect (Lead Designer) Weekly .rvt
Structural Model Structural Engineer Weekly .rvt
MEP Model MEP Engineer Weekly .rvt
Federated / Coordination Model {{Team}} {{Frequency}} {{Format}}

Tip: Keep delivery frequency realistic — consistent weekly drops are better than occasional “big” uploads.

Project Coordinates

Define the coordinate and level system so all models align correctly for coordination, verification, and exchange.

Physical Project Coordinates:
Project Datum 0,0,0
Height Datum 0.0 ft. / m
Project Location Easting: 452 780.00 Northing: 318 420.00
Project Rotation / Positioning degrees 0
Alignment rules (must follow)
  • All discipline models shall use the same coordinate and level system defined above.
  • Models must not be manually shifted to “make it fit” — coordinate issues must be resolved at source.
  • Each update replaces the previous version in the CDE (avoid parallel “final_final” versions).
  • For IFC export (if required), shared coordinates must be maintained to keep models aligned in review tools.
Why this matters

Model delivery rules ensure teams share the right information at the right time. Coordinate consistency prevents “misaligned models”, reduces rework during coordination, and supports reliable verification and handover.